No same IP for ns1.box and ns2.box

[gevik]

Hi,

So i followed the video and installed the server. My registerar does not allow box.ns1 and box.ns2 have the same ip address (they must have some reason for that). At the status check in MIAB this is also warned. Now I wonder what are the consequences to have only ns1.box point to the correct ip and ns2.box point to 1.2.3.4. Or should I just a one glue record (ns1.box)?

Any thoughts?

[murgero]

they should be the same. Can you contact them directly? they might be able to force it

[gevik]

Just asked the registerar and they cannot because the main registry does not accept this. I thought I can add a secondary IP to my DigitalOcean server but then again DO does not have that option (feels like jumping from one hoop to another)

[schotty]

I am using GoDaddy & Linode for my registrar and vps respectively. No issues with GoDaddy having that node being dns1. & dns2.

[gevik]

Thank you, I certainly will take a look at it. At the moment I have set the the dns server at the registerar to point to Cloudns, and copied the records from ns(1/2).box over Cloudns. The “System Check” is not happy about it, but it seems to work. I still need to check if this will work for the secondary domains.

[pothi]

@gevik

I thought I can add a secondary IP to my DigitalOcean server but then again DO does not have that option

You can add floating IP in DigitalOcean. It’s free too.

[gevik]

WOW, I did not know that. Thank you.

[itsbhanusharma]

@pothi

You can add floating IP in DigitalOcean . It’s free too.

That still won’t solve the warning in admin panel. It will still complain about incorrect IP for ns2

[murgero]

DO droplet with 2 IP’s MIAB will listen on both, then add ns2.box.domain.com with the second IP to GoDaddy / DNS provider

No more warnings.

[itsbhanusharma]

@murgero

No more warnings.

I still get warning for incorrect IP on ns2.box.rctngl.xyz if I configure it to my floating IP on DO! so maybe I’m missing some part of the configuration?

[murgero]

That’s pretty strange that it would, how long has it been since you set the NS record? They can take up to 48 hours to update properly.

[itsbhanusharma]

@murgero

That’s pretty strange that it would, how long has it been since you set the NS record?

What does that mean? Didn’t really get it!

[murgero]

My apologies, I’ll reword for you;

How long has it been since you set the ns1 and ns2 IP Address’s with your registrar?

[itsbhanusharma]

@murgero

How long has it been since you set the ns1 and ns2 IP Address’s with your registrar?

maybe 3 weeks! …
I just saved the settings for glue records again at my registrar and error went away though! .