| 1 |
On Tue, 19 Dec 2017 08:59:10 -0500, Michael Orlitzky wrote: |
| 2 |
|
| 3 |
> > I have used .localdomain for years without issue. VLANS |
| 4 |
> > (wifi.localdomain, lan.localdomain etc.) are great if you have the |
| 5 |
> > hardware to do it. |
| 6 |
> > |
| 7 |
> > Using non-official TLD internally shouldn't cause any problems (unless |
| 8 |
> > someone is "stupid"). |
| 9 |
> |
| 10 |
> When someone registers ".localdomain", you're going to start |
| 11 |
> sending them your private, internal traffic. |
| 12 |
|
| 13 |
If you're using .localdomain, you either have it in your host file or a |
| 14 |
local DNS service, so you should never get the public DNS address |
| 15 |
for .localdomain... unless you don't use hosts and try it when connecting |
| 16 |
your laptop via another network. |
| 17 |
|
| 18 |
|
| 19 |
-- |
| 20 |
Neil Bothwick |
| 21 |
|
| 22 |
WinErr 003: Dynamic linking error - Your mistake is now in every file |
Archives