How not to set up your DNS (part 1)

November 26, 2005

Presented in illustrations:

; dig +short ns harvest.idv.tw.
harvest.idv.tw.
www.harvest.idv.tw.
; dig +short a harvest.idv.tw.
219.84.30.59
; dig +short a www.harvest.idv.tw.
219.84.30.59

To those setting up nameservers: when people said 'have two nameservers', they did not mean 'and feel free to give them the same IP address'.

As a bonus, harvest.idv.tw has probably doubled the amount of time many DNS servers take to give up on them when 219.84.30.59 is having a wee problem.


Comments on this page:

From 216.235.140.126 at 2006-01-04 22:47:15:

One cute thing about this setup is that, since their web server is pulling double duty as a name server, web surfing clients only need query the root servers to resolve the web server's IP. This works great, so long as you don't decide to renumber your web server and forget to inform Internic, a problem I once bumped into at work.

By cks at 2006-01-06 02:48:31:

Ah, glue record hell. Thank you for prompting me to write an entry on it, TheOldGlueRecordHell.

Written on 26 November 2005.
« Making self-signed SSL certificates with OpenSSL
How not to set up your DNS (part 2) »

Page tools: View Source, View Normal, Add Comment.
Search:
Login: Password:
Atom Syndication: Recent Comments.

Last modified: Sat Nov 26 03:10:50 2005
This dinky wiki is brought to you by the Insane Hackers Guild, Python sub-branch.