DNS Trouble is killing my braincells

[infospace]

I'm havnig a lot of trouble configuring DNS.

my domain is infospace.com.sg

here's my record file.
----------------------------------------------------------
$ttl 600
@ IN SOA dns1.infospace.com.sg. root.infospace.com.sg. (
2004050727
600
600
1209600
600 )

infospace.com.sg. 14400 IN NS dns1.infospace.com.sg.
infospace.com.sg. 14400 IN NS dns2.infospace.com.sg.

ftp 14400 IN A 202.172.233.188
infospace.com.sg. 14400 IN A 202.172.233.188
localhost 14400 IN A 202.172.233.188
mail 14400 IN A 202.172.233.188
dns1.infospace.com.sg. 14400 IN A 202.172.233.188
dns2.infospace.com.sg. 14400 IN A 202.172.233.186
pop 14400 IN A 202.172.233.188
www 14400 IN A 202.172.233.188

infospace.com.sg. 14400 IN MX 10 mail



========================

somehow, when i check dnsreport, it gives this result.
---------------------
Your NS records at the parent servers are:

dns2.infospace.com.sg. [202.172.233.188] [TTL=86400] [SG]
dns1.infospace.com.sg. [202.172.233.188] [TTL=86400] [SG]

[These were obtained from sgsec.lga.net.sg]
--------------------

what seems to be the problem.??
dns2 suppose to resolve to 202.172.233.186


Please help..

[infospace]

Also,

when i add a new domain using DA,
how do i configure DNS such that it updates my dns2.
which is on another machine?

dns1.infospace.com.sg - 202.172.233.188 running DA
dns2.infospace.com.sg - 202.172.233.186 no DA. Running BIND (of course)

[DirectAdmin Support]

Hello,

[server]# dig dns2.infospace.com.sg @202.172.233.186

; <<>> DiG 9.2.1 <<>> dns2.infospace.com.sg @202.172.233.186
;; global options: printcmd
;; connection timed out; no servers could be reachedI can't connect to 186 at all.. so that might be the problem. Also, the record at 188 is returning 188 as the IP for dns2.

John

[jlasman]

Originally posted by infospace
when i add a new domain using DA,
how do i configure DNS such that it updates my dns2.
which is on another machine?
You don't; that's not built into DNS.

I'll be releasing a script which you can run on a generic linux/unix system running bind, which will do it, but it'll be a while, yet.

In the meantime, you need to:

a) register 202.172.233.186 with your registrar who registered dns2.infospace.com.sg. It doesn't look as if this was done.

b) make sure that every domain using dns2.infospace.com.sg has an NS record for it in it's own dns zone3.

c) on the slave system create a slave zone reference in named.conf, and reload or restart the slave system.

Jeff

[infospace]

Originally posted by DirectAdmin Support
Hello,

[server]# dig dns2.infospace.com.sg @202.172.233.186

; <<>> DiG 9.2.1 <<>> dns2.infospace.com.sg @202.172.233.186
;; global options: printcmd
;; connection timed out; no servers could be reachedI can't connect to 186 at all.. so that might be the problem. Also, the record at 188 is returning 188 as the IP for dns2.

John

below is the entry in my file var/named/infospace.com.sg.db

dns1.infospace.com.sg. 14400 IN A 202.172.233.188
dns2.infospace.com.sg. 14400 IN A 202.172.233.186

I have already stated that i want dns2 to point to 186.
how come it is still returning 188 as IP for dns2 as you mentioned?

thanks for the assistance guys.

[jlasman]

Because you've got it assigned incorrectly.

A whois for the domain shows:

Name Servers:
dns1.infospace.com.sg
202.172.233.188

dns2.infospace.com.sg
202.172.233.188

You've got to register the proper IP# with your domain registry, as I mentioned in my previous email.

Jeff

[infospace]

One last thing.

rndc reload infospace.com.sg

does not seem to be working.
no error message, but still, the file
var/named/infospace.com.sg.hosts is empty.
in fact, no such file created at all..

[DirectAdmin Support]

Hello,

DA creates: /var/named/infospace.com.sg.db

John

[jlasman]

Infospace I have no idea why you posted the contents of your files.

I didn't bother to try to read them.

Did you fix the IP# of the server at your registrar as I wrote previously?

If you don't, it won't ever work.

Jeff

[infospace]

hi guys.

sorry for the messyiness of this thread. I apologise.

found the root of evil already.
The registrars dnschanging form has a bug and captures the wrong IP entered by their users.

that's why. have since fixed it.
thanks so much.