James,

Thank you very much, that looks like exactly what I was after. I'll keep it in mind the next time this comes up.

I ended up purchasing DNS hosting as my registrar didn't seem to be able to set the glue records up properly.

Regards,
Ashley Glenday

* The time for my yearly haircut is coming around again (March
11th-13th). If anyone wants to sponsor me they can make a tax
deductible donation at:
http://my.imisfriendraising.com.au/personalPage.aspx?SID=91562 All
money raised goes to the Leukemia Foundation. *

** I will be out of the country between 1st April and 20th April.
During this time I can still be reached by email, but will be without
mobile contact **

I am now offering after hours services.
7am-9am and 5pm-11pm Weekdays
and all day Saturday and Sunday.
The after hours number is: 02 4786 0736
New charges will apply
Telephone support - $50
Remote support - $100
Onsite support - $200 p/h or part thereof

On 26/02/10 10:20, James Polley wrote:
My favorite tool (which has some limitations, but is usually a good
start) is dnstracer.

oll...@ppgnte-ubiq43:~$ dnstracer -s b.root-servers.net -o  -4 www.smh.com.au
Tracing to www.smh.com.au[a] via b.root-servers.net, maximum of 3 retries
b.root-servers.net (192.228.79.201)
  |\___ UDNS1.AUSREGISTRY.NET.au [au] (156.154.100.18)
  |     |\___ ns4.fairfax.com.au [smh.com.au] (203.58.234.244) Got
authoritative answer [received type is cname] [received type is cname]
  |     |\___ ns2.fairfax.com.au [smh.com.au] (203.5.59.241) Got
authoritative answer [received type is cname] [received type is cname]
  |      \___ ns1.fairfax.com.au [smh.com.au] (203.26.177.241) Got
authoritative answer [received type is cname] [received type is cname]
  |\___ NS2.AUDNS.NET.au [au] (58.65.249.73)
  |     |\___ udns2.ausregistry.net.au [com.au] (156.154.101.18)
  |     |     |\___ ns1.fairfax.com.au [smh.com.au] (203.26.177.241) (cached)
  |     |     |\___ ns4.fairfax.com.au [smh.com.au] (203.58.234.244) (cached)
  |     |      \___ ns2.fairfax.com.au [smh.com.au] (203.5.59.241) (cached)
  |     |\___ udns1.ausregistry.net.au [com.au] (156.154.100.18) (cached)
<<lots of cached results skipped>>
ns1.fairfax.com.au (203.26.177.241)     www.smh.com.au ->
dsa.f2.com.au.edgesuite.net
ns1.fairfax.com.au (203.26.177.241)     dsa.f2.com.au.edgesuite.net ->
a1040.b.akamai.net
ns2.fairfax.com.au (203.5.59.241)       www.smh.com.au ->
dsa.f2.com.au.edgesuite.net
ns2.fairfax.com.au (203.5.59.241)       dsa.f2.com.au.edgesuite.net ->
a1040.b.akamai.net
ns4.fairfax.com.au (203.58.234.244)     www.smh.com.au ->
dsa.f2.com.au.edgesuite.net
ns4.fairfax.com.au (203.58.234.244)     dsa.f2.com.au.edgesuite.net ->
a1040.b.akamai.net


If you're having issues with glue, or one of your NSes is serving
dodgy records, this will usually catch this - you'll see that ns1
returns one set of results while ns2 returns another; or you'll see
that the .com.au servers are returning the wrong glue, etc.

Which reminds me:

poll...@ppgnte-ubiq43:~$ dnstracer -s b.root-servers.net -o  -4 zhasper.com
Tracing to zhasper.com[a] via b.root-servers.net, maximum of 3 retries
b.root-servers.net (192.228.79.201)
  |\___ M.GTLD-SERVERS.NET [com] (192.55.83.30)
  |     |\___ ns2.zilence.com.au [zhasper.com] (203.27.221.213) Refers backwards
  |      \___ ns1.zilence.com.au [zhasper.com] (88.198.1.123) Got
authoritative answer

I really need to fix my own dns hosting. I should go back and read
that other thread about secondary hosting..


On Sat, Feb 20, 2010 at 11:56 AM, John Ferlito<[email protected]>  wrote:
On Fri, Feb 19, 2010 at 11:12:44PM +1100, Ashley Glenday wrote:
At the beginning of this saga I had a server in America that I
called ns1.domain.com and ns2.domain.com. After this I decided to
become patriotic (with the help of some sluggers suggestions) and
moved to a host in Sydney, this server became ns3.domain.com and
ns4.domain.com. My problem is that it's time to move yet again and I
wanted to go back to ns1.domain.com and ns2.domain.com but this
doesn't seem to work. My registrar assures me they've set the glue
records up properly but I can't get it to resolve. The host has set
the reverse DNS up as I can confirm that with host 123.123.123.123
which returns ns1.domain.com

What I'm after is any known way to test the glue records are in fact
set up properly and if they are, what else could I have missed?

So for google If I wanted to check I would do



jo...@zoot:~$ dig ns google.com
;; ANSWER SECTION:
google.com.     296819  IN  NS  ns4.google.com.
google.com.     296819  IN  NS  ns2.google.com.
google.com.     296819  IN  NS  ns1.google.com.
google.com.     296819  IN  NS  ns3.google.com.

jo...@zoot:~$ dig soa com
;; ANSWER SECTION:
com.            789 IN  SOA a.gtld-servers.net.  nstld.verisign-grs.com. 
1266627161 1800 900 604800 86400

jo...@zoot:~$ dig a ns1.google.com. @a.gtld-servers.net.
;; ANSWER SECTION:
ns1.google.com.     172800  IN  A   216.239.32.10


If there is no glue record the ANSWER section will be empty and you'll
get a WARNING about recusrion being disabled.

Cheers,
John


--
John
Blog                             http://www.inodes.org
LCA2010                          http://www.lca2010.org.nz
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

<<attachment: ashley.vcf>>

-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Reply via email to