Domain landing on shared IP, but Virtual Server has private

Help! (Home for newbies)
1

Hi,

In VirtualMin have a Virtual Server setup for domain.com, and said domain.com is pointing to the VPS no problem.

The Virtual Server has a private IP address.

The VPS as a whole has a few other IP addresses too, including the main ‘shared’ ip.

The domain.com is going to the shared IP address of the VPS as a whole, where it should be going to the Private IP for this Virtual Server.

I have probably missed a setting somewhere, but cannot figure out what.

In Edit Virtual Server, the ‘external IP address’ is set to the private one.
In Server Config > Change IP address, is it set to the private one.
In Servers > DNS Domain, the A records are set to the private one (the NS record is set to the address of VPS as a whole)

So, as far as I can tell, everything is telling it to be the private IP… but the domain still ends up on shared IP…

What have I missed?

Thanks
Rob

EDIT: PS I have BIND DNS server within the Webmin setup, but have no real idea what I’m doing in there…

2

Hey

I think I know the issue, the DNS Zone simply had the shared server IP address for it’s A and MX records.

So I tried to update them to the correct private IP… but it hasn’t worked. For some reason, they are still, according to traceroute, locked to the shared IP. However looking in the DNS Zone from my provider, it is set (at least in the provider’s settings) the the correct, private IP… Thought it was propogation issue, but it’s not that…

Humz!

3

Howdy,

DNS can be a little funny about that… DNS entries are generally cached for some amount of time.

Once you do a DNS lookup (ie, if you browse to “www.example.com”), that DNS entry can be cached in your ISP’s DNS for a day or two.

If you recently changed that domain’s IP address, you may need to wait until the cache has cleared from all the DNS servers that cached that entry.

Until then – those DNS servers may be giving you the old IP address they obtained before you changed it.

-Eric

4

Howdy,

DNS can be a little funny about that… DNS entries are generally cached for some amount of time.

Once you do a DNS lookup (ie, if you browse to “www.example.com”), that DNS entry can be cached in your ISP’s DNS for a day or two.

If you recently changed that domain’s IP address, you may need to wait until the cache has cleared from all the DNS servers that cached that entry.

Until then – those DNS servers may be giving you the old IP address they obtained before you changed it.

-Eric

5

Hey,
Is there anything in Virtualmin that would hold onto DNS settings and not allow changes done elsewhere (by main dns provider) to work?

I understand propagation times, issue is that other domains have switched in about 30 minutes (it’s essentially all on the same server, so propagation is pretty quick), but this one in question has been 22 hours+ so I’m thinking something else is up.

Cheers

6

Is there anything in Virtualmin that would hold onto DNS settings and not allow changes done elsewhere (by main dns provider) to work?

Well, DNS should only ever be managed from one place.

So, if your DNS is hosted by your Virtualmin server – that would mean DNS should only ever be changed by your Virtualmin server, you ISP shouldn’t be involved.

On the other hand, if your ISP is managing your DNS – Virtualmin should then be configured to not do DNS since it’s done elsewhere. In that case, you’d need to make sure that in System Settings -> Features and Plugins, that “DNS for Domain” is disabled. If it’s not, you could end up with conflicting DNS entries.

-Eric

7

Hey,

Thanks for the reply.

At one stage, I did have DNS hosted by Virtualmin, but then I turned it off thinking that was causing problems, but issue still remained.

Anyway, I reverted back to using the DNS of the domain name provider and simply making my own A records to point to the correct IP, so all good now

Thanks