i just set up a domain name server (my first) on my domain. i'm pretty sure it's correctly configured. i got a secondary dns through twisted4life.com and registered both the primary and secondary dns with my registrar.

when i run dig from a remote machine, i get this:

dig www.mydomain.com

; <<>> DiG 9.2.2-P3 <<>> www.mydomain.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19673
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.mydomain.com. IN A

;; ANSWER SECTION:
www.mydomain.com. 85232 IN CNAME ns.mydomain.com.
ns.mydomain.com. 85232 IN A xxx.xxx.xxx.152

;; Query time: 25 msec
;; SERVER: 129.109.1.207#53(129.109.1.207)
;; WHEN: Thu Jan 8 12:56:05 2004
;; MSG SIZE rcvd: 67

here's what i think the problem is: xxx.xxx.xxx.152 should be xxx.xxx.xxx.153. i've registered ns.mydomain.com as xxx.xxx.xxx.153 with the registrar (and called back to verify this info), so i'm suprised it shows xxx.xxx.xxx.152. i've contacted my isp and xxx.xxx.xxx.152 is actually my broadcast ip.

i guess i don't understand the process fully enough to know where the problem lies. what exactly does my registrar have to configure on their end? they say everything's configured correctly. i thought he said he gives this info to verisign. so could it be a mistake on verisign's part?

thanks for any help,
jason

It wouldn't be the first time the ip numbers have been entered badly..

(if 152 is your broadcast address, your actual number will be lower)

Keep on at them frequently to correct it.
It may take some hours to propogate into the wider world and they may only update the main dns once a day...

thanks for the reply. since my post i've found a mistake in my domain name server and corrected it. now it works, but only locally with my /etc/resolve.conf set to search mydomain.com and use my ISPs DNS.

dig www.mydomain.com

; <<>> DiG 9.2.2-P3 <<>> www.mydomain.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45924
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.mydomain.com. IN A

;; ANSWER SECTION:
www.mydomain.com. 10723 IN CNAME ns.mydomain.com.
ns.mydomain.com. 10723 IN A xxx.xxx.xxx.152

;; Query time: 17 msec
;; SERVER: 129.109.1.207#53(129.109.1.207)
;; WHEN: Fri Jan 9 09:37:58 2004
;; MSG SIZE rcvd: 67

the reverse lookup also works as it should.

but when i use my computer at work, which is set to search a different domain and use a different DNS, it doesn't work. it gives the same results as in the first post and the reverse lookup doesn't work. how could that be?

The time delay in the original dns server sending updates globally..

Some are up to 4-5 days...

And even an operator making a change and not updating the record's serial number, so the update is ignored..

wait a minute... so you're telling me that after i reconfigure the named.conf file on my domain name server, the changes will automatically propogate throughout the internet? seems a bit strange. i thought i'd have to send it to the centralized registry or something. again, this shows my lack of understanding about what exactly my registrar is responsible for regarding dns.