Accessing an AD/Domain that is Currently Out of the Guest Network.

Product Line: VERDE

There may be a need to access and authenticate with an AD Server/Domain Server that is Out of the Guest Network. These setting are specific to VERDE. Add/Edit the lines highlighted.

/etc/hosts

127.0.0.1 localhost4 localhost4.localdomain4
10.0.1.4 localhost localhost.localdomain
10.0.1.5 verde.local <--- AD/Domain Server IP and FQDN

/etc/resolve.conf

; generated by /usr/sbin/dhclient-script
search o2pqmddjl05uzloljld30zop1c.dx.internal.cloudapp.net
nameserver 168.63.129.16
nameserver 10.0.1.5 <--- AD/Domain Server IP

/usr/lib/verde/etc/samples/dhcpd.conf.template

ddns-update-style ad-hoc;
option subnet-mask 255.255.255.0;
option wpad code 252 = text;
option wpad "\n\000";
default-lease-time 300;
max-lease-time 300;
authoritative;

subnet SUBNET.0 netmask 255.255.255.0 {
range SUBNET.1 SUBNET.200;
option broadcast-address SUBNET.255;
option routers SUBNET.254;
option domain-name-servers 10.0.1.5; <--- AD/Domain Server IP
option domain-name "verde.local"; <----FQDN
}