Gregory's Server
There's always at least one person who doth protest too loudly, whenever they are alerted to bad habits like these π
|
6 comments
 @sindarina @sindarina @sebastian @sindarina I know of a network equipment vendor which used a real, public address block belonging to a real, much larger company internally in a product they shipped. There were a few companies which were customers of both. Hilarity ensued. The same network equipment vendor now uses 192.0.2 internally in a major product. Their reasoning is nobody should be using it, therefore *they* should use it.  when i was doing tech support for an open source DNS server, we regularly got support customers wondering why using fake roots or fake DNS names that collided with the public DNS kept breaking things. i also worked for a large ISP that really pushed using IPv6 because they'd had problems in their NOC with many reuses of RFC1918 space and address collisions. RFCs are not for the faint of heart but they have lots of good info and lots of reasons why you should follow them. ;) |
ADDENDUM: If you need to generate reverse DNS records for IP addresses, DO NOT simply paste in the entire IPv4 address as the hostname, such as in this example;
β 198.51.100.1.net.example
β 198.51.100.2.net.example
If you absolutely need to use dots, like for delegation within a large enterprise or to clients, reverse the string instead;
β 1.100.51.198.rev.net.example
β 2.100.51.198.rev.net.example
Most to least specific, always.
In the vast majority of cases, keep it simple, with something like this;
β ip-198-51-100-1.dhcp.net.example
β ip-198-51-100-2.dhcp.net.example
Can be delegated if needs be, and is clearly separate.
ADDENDUM: If you need to generate reverse DNS records for IP addresses, DO NOT simply paste in the entire IPv4 address as the hostname, such as in this example;
β 198.51.100.1.net.example
β 198.51.100.2.net.example
If you absolutely need to use dots, like for delegation within a large enterprise or to clients, reverse the string instead;