SV: panel error *** ORBit patch ***
- From: "Stefan Skoglund" <hlz522w tninet se>
- To: "gnome-list" <gnome-list gnome org>
- Subject: SV: panel error *** ORBit patch ***
- Date: Sat, 15 Aug 1998 15:34:17 +0200
>Not really. One host can have more then one hostname (think of multuple
>ethernet cards, each with a different reverse DNS. Fun, yes. I think the
>packet-to-self method is the only reliable method. I wonder if people who
>aren't crazy would have thought of it.)
>
Lets say we have two networks A and B.
3 machines a,b,c. b is multihomed ie has one ethernet-interface
at both networks.
The networks is connected with a brouter so b doesn't run IPfw.
Network A is 192.168.1.xx
-"- B is 192.168.2.xx
a has adress 192.168.1.1
b has adress 192.168.1.2 on network A
and adress 192.168.2.2 on network B
c has adress 192.168.2.1
a is known as a.localdomain
b is known as b.localdomain
c dito
b runs dns. What now ? a should be able to send requests to its dns server
for the IP-adress of b and c using the hostname b and c
c should be able to send requests to its dns server
for the IP-adress of b and a using the hostname b and a.
The reply to a with the adress of b should be a local adress ie 192.168.1.2
and c in the same case should get 192.168.2.2 ie the different answers to
the same
question if not for the source.
Which will happen if name-resolving on clients and dns server is correct.
This way messages to b doesn't need to go thru the brouter.
Reverse lookup on 192.168.2.2 and 192.168.1.2 should get the same answer ie
b.localdomain which is the main reason why getnamebyaddr must work.
Puhhhh
----------------------------------------------------------------------------
----
Stefan Skoglund hlz522w@tninet.se
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]