loopforever
Verified User
Hi John,
I recently had a problem with a reseller with their own nameservers. After a named update, the service was restarted and his particular domain failed to load, all kinds of nslookup funniness. Once I looked at his zone file, I saw the issue: an underscore in a hostname of an A record.
named won't complain on restart, but all records following the _ do not get interpreted.
I removed the A record containing the _, restarted named, problem solved.
Not sure if anyone else has had this problem (running DA 1.32.0) - but records containing _ should not be permitted via the DNS forms on the panel.
Hope all is well with you guys! Talk to you later!
I recently had a problem with a reseller with their own nameservers. After a named update, the service was restarted and his particular domain failed to load, all kinds of nslookup funniness. Once I looked at his zone file, I saw the issue: an underscore in a hostname of an A record.
named won't complain on restart, but all records following the _ do not get interpreted.
I removed the A record containing the _, restarted named, problem solved.
Not sure if anyone else has had this problem (running DA 1.32.0) - but records containing _ should not be permitted via the DNS forms on the panel.
Hope all is well with you guys! Talk to you later!