How not to set up your DNS (part 3)

November 28, 2005

Presented once again in illustration:

; sdig ns isotech.com.cy
dns2.lordosinfo.com.
dns1.lordosinfo.com.
; sdig ns lordosinfo.com.
dns1.edynet.com.cy.
dns1.lordosinfo.com.
; sdig ns edynet.com.cy.
dns2.netconnect.com.cy.
dns1.netconnect.com.cy.

At the moment:

  • dns2.netconnect.com.cy is not responding,
  • dns1.edynet.com.cy doesn't exist according to dns1.netconnect.com.cy,
  • dns2.lordosinfo.com is a CNAME to outopos.lordosinfo.com,
  • and outopos.lordosinfo.com is a CNAME to itself (that's good for bonus points).

In the face of all of this, our DNS server is currently laughing hysterically at the very idea of looking up A and MX records for isotech.com.cy. (In fact it bitches about 'protocol error', possibly due to the nice CNAME loop.)

Written on 28 November 2005.
« What Python's global interpreter lock does (and doesn't) protect
A little gotcha in shell scripts »

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

Last modified: Mon Nov 28 15:19:55 2005
This dinky wiki is brought to you by the Insane Hackers Guild, Python sub-branch.