This will be a fault where the world uses you public IP to access your zone hosted on your server, but when your server tries to resolve dns1.buehlertech.net it is not contactable (probably because of NAT on a firewall) and so tries dns2.buehlertech.net, but it is also not contactable. Then it goes back to the root to try again, but of course there is no way you can talk to yourself via a public IP.
I may have got a little bit of the process wrong, but in essence it is correct. If anyone can talk to you, but you can't talk to you, then it will be NAT. Try BIND views, or hosting on a different server, or allowing dns resolution from 127.0.0.1, then pointing resolv.conf to 127.0.0.1 Rob :-) _________________________________________________ It might look like I'm doing nothing, but on a cellular level, I'm quite busy. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Buehler Sent: Saturday, February 23, 2008 11:36 AM To: [email protected] Subject: [xmail] Re: FreeBSD problem (similar to NetBSD problem report ed earlier?) Hi Davide - Sorry about the delay on this - I was in away yesterday and today... Here is a sample of the dig + trace - I copied only the last two entries - basically this pattern is repeated until the "too many lookups" result. The other domains this server is authoritative for produce the same result except for buehlertech.net and buehlertech.com which work fine. The only differences I can think of is the reverse points to buehlertech.net and the domain is buehlertech.net in resolv.conf and in the hosts file (but why would buehlertech.com work?). ;; Received 117 bytes from 192.5.6.30#53(a.gtld-servers.net) in 126 ms com. 21365 IN NS e.gtld-servers.net. com. 21365 IN NS f.gtld-servers.net. com. 21365 IN NS g.gtld-servers.net. com. 21365 IN NS h.gtld-servers.net. com. 21365 IN NS i.gtld-servers.net. com. 21365 IN NS j.gtld-servers.net. com. 21365 IN NS k.gtld-servers.net. com. 21365 IN NS l.gtld-servers.net. com. 21365 IN NS m.gtld-servers.net. com. 21365 IN NS a.gtld-servers.net. com. 21365 IN NS b.gtld-servers.net. com. 21365 IN NS c.gtld-servers.net. com. 21365 IN NS d.gtld-servers.net. ;; Received 504 bytes from 67.102.108.82#53(dns1.buehlertech.net) in 68 ms trikorausa.com. 172800 IN NS dns1.buehlertech.net. trikorausa.com. 172800 IN NS dns2.buehlertech.net. ;; Received 117 bytes from 192.12.94.30#53(e.gtld-servers.net) in 93 ms com. 21365 IN NS c.gtld-servers.net. com. 21365 IN NS d.gtld-servers.net. com. 21365 IN NS e.gtld-servers.net. com. 21365 IN NS f.gtld-servers.net. com. 21365 IN NS g.gtld-servers.net. com. 21365 IN NS h.gtld-servers.net. com. 21365 IN NS i.gtld-servers.net. com. 21365 IN NS j.gtld-servers.net. com. 21365 IN NS k.gtld-servers.net. com. 21365 IN NS l.gtld-servers.net. com. 21365 IN NS m.gtld-servers.net. com. 21365 IN NS a.gtld-servers.net. com. 21365 IN NS b.gtld-servers.net. ;; Received 504 bytes from 67.102.108.82#53(dns1.buehlertech.net) in 54 ms trikorausa.com. 172800 IN NS dns1.buehlertech.net. trikorausa.com. 172800 IN NS dns2.buehlertech.net. dig: too many lookups Jeff Davide Libenzi wrote: > On Thu, 21 Feb 2008, Jeff Buehler wrote: > > >> By the way, the trace does, and always has, produced the correct name >> servers (dns1.buehlertech.net and dns2.buehlertech.net), it just >> continues to trace after that result. >> > > Do they set the correct AUTHORITY bit in the answer? > > > > - Davide > > > - > To unsubscribe from this list: send the line "unsubscribe xmail" in > the body of a message to [EMAIL PROTECTED] > For general help: send the line "help" in the body of a message to > [EMAIL PROTECTED] > > - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
