I need to create private nameservers, but I don't want to use my real IP address when creating them. I want to use just some generic non-functional IP address. Will the process allow me to just enter something like 123.123.1.1 and actually create the nameservers without any error messages?

No, I haven't been sniffing any glue today. :D

The reason for this strange question is that I need to produce some tutorials on how to create private nameservers. And I don't want to use any real IP addresses that relate to any specific hosting company. I need to keep it as generic as possible.

So any suggestions on what IPs I should use?

Vito

Why not just use real IPs to start and then edit them out of the Flash animation?

Yes, I can do that if I have to. I'm just trying to make it easier and more efficient. I have to produce at least a dozen of these movies so I'm trying to cut down on the repetetive work.

If need be, I'll do as you suggested. But I would like to know if I can just put in any IP and have it work.

Vito

It definitely won't really work if you put in fake IPs obviously, but some control panels might accept fake IPs without complaining. I'd guess that most would want the IPs to be binded to the machine you are working on or at least check remote IPs for the presence of a nameserver and then establish a trust relationship. Why not just give it a shot and see what happens? Sounds like it would probably be easier just to edit the IPs out of the animation.

Thanks, John. I guess I'll just have to try it on a registrar by registrar basis. If it allows me, great. If not, I do some post production editing.

Thanks for the input. :)

Vito

No problem. Big fan of your tutorials BTW.. we use them on our site and I look forward to seeing your new nameserver tuts. :) Keep up the good work.

Hmmf. I just tried it (in Enom) with a fake IP (127.0.0.1) and it gave an error saying it was a restricted IP. I guess I'm just going to have to use a real IP on my box, and then edit afterwards... :mad:

Vito

why not 192.168.0.1? :-P

That IP belongs to IANA.

Can you explain further?

Vito

I thought that was for Private networks? :confused:

Umm, OK. I'm not sure I understand that. (I have a really hard time understanding DNS and all its nuances...) So are you saying that will work if I use that when creating nameservers?

Vito

Just as 127.0.0.1 is reserved/restricted for the "loopback" adapter, 192.168.0.1 is reserved for private networks (LANs). I doubt it will work.

Originally posted by John[H4Y]
Just as 127.0.0.1 is reserved/restricted for the "loopback" adapter, 192.168.0.1 is reserved for private networks (LANs). I doubt it will work.

Yep, it's for local networks. There's certain IPs that are reserved for local networks, that users on other networks can't connect to. If you have a home broadband router, it might be 192.168.0.1, and then each PC would be assigned 192.168.0.2, 192.168.0.3, and so on. If someone on another LAN tried connecting to one of those IPs, they wouldn't be able to as they're assigned locally - not globally.

I know the following IPs are private:

192.168.*.*
127.*.*.*
10.*.*.*

There's probably other ranges that are private too, I just don't know which.

You could always create the nameservers using real IPs if the reserved ones keep getting turned down - and then blur the IPs or Photoshop it with the private IPs afterwards.

Thats technically incorrect, from RFC 1918:

10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)