Topic awaiting preservation: DNS Try Again (Page 1 of 1)

I have the domain name codetown.org and I believe that I have things set up somewhat correctly. Using godaddy I have set my name servers to ns1.66.67.196.34 and ns2.66.67.196.34. I then set up my router to forward packets addressed to port 53 to the machine running the bind (both TCP and UDP packets).

Something is wrong though. If I dig on the localhost I get the following:

dig @127.0.0.1 codetown.org



; <<>> DiG 8.3 <<>> @127.0.0.1 codetown.org 

; (1 server found)

;; res options: init recurs defnam dnsrch

;; got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36936

;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUERY SECTION:

;;      codetown.org, type = A, class = IN



;; ANSWER SECTION:

codetown.org.           1H IN A         66.67.196.34



;; AUTHORITY SECTION:

codetown.org.           1H IN NS        ns1.codetown.org.

codetown.org.           1H IN NS        ns2.codetown.org.



;; ADDITIONAL SECTION:

ns1.codetown.org.       1H IN A         66.67.196.34

ns2.codetown.org.       1H IN A         66.67.196.34



;; Total query time: 0 msec

;; FROM: roc-66-67-196-34.rochester.rr.com to SERVER: 127.0.0.1

;; WHEN: Sun Mar 14 19:02:18 2004

;; MSG SIZE  sent: 30  rcvd: 114

Which is correct. Everything looks right to me. This is when I stay at the local computer, and don't go outside of the router. No problems. However when I try dig without specifying the local machine I get the following error:

dig codetown.org



; <<>> DiG 8.3 <<>> codetown.org 

;; res options: init recurs defnam dnsrch

;; got answer:

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 11807

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUERY SECTION:

;;      codetown.org, type = A, class = IN



;; Total query time: 12 msec

;; FROM: roc-66-67-196-34.rochester.rr.com to SERVER: 24.93.1.118

;; WHEN: Sun Mar 14 19:01:32 2004

;; MSG SIZE  sent: 30  rcvd: 30

I don't have a clue why this is happening. I made a test program that would send a UDP packet to my computer from an external shell acount and the UDP packet is sucessful in connecting through the router. On a port scan of my IP using http://scan.sygate.com/prequickscan.html it shows that DNS is open for TCP/IP which I have set up because it might be needed for malformed DNS queries and zone transfers. When running the UDP scan I get an error telling me that UDP packets are all being blocked. I don't know why this is happening.

I really don't know what might be wrong.

Any help would be appreciated.

-Dan-

First, I'm not getting name resolution for codetown.org. That's probably because I'm not getting responses from either NS.



[This message has been edited by Pugzly (edited 03-15-2004).]

Yeah, that is where being a DNS newbie is killing me. I don't know what I have done wrong with setting this up so that I don't get a correct resolution...

-Dan-

WarMage: It looks to me like your name server names are not correct. I think the server name should look like NS1.AMSNAC4.COM. It looks to me as if you have combined the NS domain name with the IP address.




-- not necessarily stoned... just beautiful.

I was wondering about that.

What should be the name server address I have to give godaddy? Since I am hosting the name server myself and the only address I have is my IP address, or that which was supplied by the ISP which is roc-66-67-196-34.rochester.rr.com?

I tried giving godaddy just the IP address but they didn't like that either.

Currently I am reading DNS and Bind and hopefully I will pick something up there. I would figure that in 4 year of college studying computer science DNS would have come up somewhere in the course load. Turns out that this DNS stuff is really involved, and somewhat tricky.

-Dan-

If you're hosting it yourself, you have to be running a DNS solution locally. OR, you could use something like dynip.

But you need that NS record to point to an actual DNS server.

The domain name record points to a DNS server that actually does the resolution. Once you have a DNS solution in place, you can create the appropriate records for that domain.

Contact me offline if you need help. I deal with DNS stuff all day.

Just wanted to bring up that I solved my problem. I didn't know origionally that I had to register my IP address as a name server with the Registrar. Your not allowed to simply point your domain at an IP address you have to register the IP address and then point the domain at the name you supplied when you registered the IP.

All is up and working now. http://www.codetown.org is up and running. I am sure I have made hundreds of small mistakes but for my first time setting up and running a complete hosting kit of email, ssh, sftp, web, and dns I think I did ok. Thanks a lot all for all the help!

Dan
CodeTown.org