PDA

View Full Version : NameServer Problem


Wilsonctc
08-07-2005, 07:02 PM
I would want to know that, is the status of nameserver MUST be free ? It cannot be "SERVER" ?
jmstacey
08-07-2005, 08:59 PM
If you could elaborate on your problem, it might give us a better idea of the situration.

You should be able to set nameservers on any IP address as long as no other nameservers are currently assigned to those IP addresses.
Wilsonctc
08-07-2005, 09:15 PM
jmsyecay, I have pm you.
nobaloney
08-08-2005, 03:50 PM
Jon,

I'm not sure in what context you mean; please explain.

We have clients who use their own nameservers, and they just use the same IP#s we use for our nameservers.

Jeff
jmstacey
08-08-2005, 05:28 PM
Non-virtual is what I meant to say.
Unless your adding the nameservers as virtual nameserver, you can't add mutliple nameservers to an IP address (from the Nameserver page on the reseller level)

This is one of my weakest areas, but my guess would be because he's using a non-standard TLD (.hk). I suggested he ask you for a more definate answer.
nobaloney
08-08-2005, 08:37 PM
As far as I know the only difference between a virtual nameserver and a (non-virtual) nameserver is one of semantics. A virtual nameserver is a nameserver with a different name pointing at the same IP as an already running nameserver.

I don't see any issues at all with running "virtual nameservers" on the same IP#.

Do you? Does anyone?

Jeff
jmstacey
08-13-2005, 02:45 PM
I can look into this problem with gusto now, that it's happening to me after a recent hostname and nameserver change.

I'm pretty sure it's a problem with bind/named on the local server. All my research has turned up that the nameservers are registered properly and are pointing to the corrct IP addresses and are succesfully contacting the parent server, however the service doesn't respond even with failure.
No firewalls etc.

I'll keep digging.
jmstacey
08-14-2005, 08:53 PM
It seems to be a problem with my current DC (who should remain nameless), however they are not resolving the issue fast enough so I'm in the process of moving to a new one.
(one of their routers is malfunctioning and their not shall I say hopping to it to fix it.)
:rolleyes: