Hey Guys, Was wondering if anyone could help out with this. Just two days ago we started to experience DNS problems resolving international addresses. The DNS servers are configured with no forwarders and go directly out. We can resolve NZ addresses but nothing else. Norhing's changed on the DNS severs and the problem just started happening. Link is going out on Citylink through to ICONZ. Any ideas? or help? Cheers J
intergen.co.nz Server: ns1.eaglegis.co.nz Address: 210.48.106.196
Name: intergen.co.nz Address: 202.49.144.165
google.com Server: ns1.eaglegis.co.nz Address: 210.48.106.196
DNS request timed out. timeout was 2 seconds. *** Request to ns1.eaglegis.co.nz timed-out
nzpost.co.nz Server: ns1.eaglegis.co.nz Address: 210.48.106.196
Name: nzpost.co.nz Address: 202.12.249.9
On 4-Aug-2006, at 18:20, Jithen Singh wrote:
Was wondering if anyone could help out with this. Just two days ago we started to experience DNS problems resolving international addresses. The DNS servers are configured with no forwarders and go directly out.
From the DNS servers themselves, choose a name that doesn't seem to work and send the query individually to authority servers from the root down, using both UDP and TCP transport, with "recursion desired" set to 0. For example: $ dig @f.root-servers.net google.com A +norec (observe delegation to Verisign servers) $ dig @a.gtld-servers.net google.com A +norec (observe delegation to google servers) $ dig @<insert google server here> google.com A +norec (observe answer from google server) Repeat with "+tcp" on the end, to force TCP transport. Repeat with all nameservers in each NS set. As a shortcut, dig's +trace option might be useful (but note that dig +trace doesn't query all servers in an NS set, just one of them). Joe
Is your name server using the IP address you think it's using? If it's
on Citylink and has a WIX address as well as 210.48.106.196, you may
find that the actual address the queries use is the WIX address, which
isn't globally routable. The same applies to non-routable link
addresses.
If your name server does have multiple IP addresses that's the case, you
can force BIND to make queries using your host's "official" address
using:
query-source address 210.48.106.196 port *;
within your options { ... } block.
-- don
Jithen Singh
Hey Guys,
Was wondering if anyone could help out with this. Just two days ago we started to experience DNS problems resolving international addresses. The DNS servers are configured with no forwarders and go directly out. We can resolve NZ addresses but nothing else. Norhing's changed on the DNS severs and the problem just started happening.
Link is going out on Citylink through to ICONZ. Any ideas? or help?
Cheers J
intergen.co.nz Server: ns1.eaglegis.co.nz Address: 210.48.106.196
Name: intergen.co.nz Address: 202.49.144.165
google.com Server: ns1.eaglegis.co.nz Address: 210.48.106.196
DNS request timed out. timeout was 2 seconds. *** Request to ns1.eaglegis.co.nz timed-out
nzpost.co.nz Server: ns1.eaglegis.co.nz Address: 210.48.106.196
Name: nzpost.co.nz Address: 202.12.249.9
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
Have now fixed the issues that were occurring. Thanks for all the help from everyone. Cheers Don Stokes wrote:
Is your name server using the IP address you think it's using? If it's on Citylink and has a WIX address as well as 210.48.106.196, you may find that the actual address the queries use is the WIX address, which isn't globally routable. The same applies to non-routable link addresses.
If your name server does have multiple IP addresses that's the case, you can force BIND to make queries using your host's "official" address using:
query-source address 210.48.106.196 port *;
within your options { ... } block.
-- don
Jithen Singh
wrote: Hey Guys,
Was wondering if anyone could help out with this. Just two days ago we started to experience DNS problems resolving international addresses. The DNS servers are configured with no forwarders and go directly out. We can resolve NZ addresses but nothing else. Norhing's changed on the DNS severs and the problem just started happening.
Link is going out on Citylink through to ICONZ. Any ideas? or help?
Cheers J
intergen.co.nz
Server: ns1.eaglegis.co.nz Address: 210.48.106.196
Name: intergen.co.nz Address: 202.49.144.165
google.com
Server: ns1.eaglegis.co.nz Address: 210.48.106.196
DNS request timed out. timeout was 2 seconds. *** Request to ns1.eaglegis.co.nz timed-out
nzpost.co.nz
Server: ns1.eaglegis.co.nz Address: 210.48.106.196
Name: nzpost.co.nz Address: 202.12.249.9
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
participants (3)
-
Don Stokes
-
Jithen Singh
-
Joe Abley