Return to Answer

It's the PTR record (reverse DNS) corresponding to the IP address which your computer was assigned via DHCP. It changes each time your computer gets a new address from DHCP and you can't make it static.

The problem here is not in the settings on your computer, but on all the other computers connected to the campus network (i.e. computers try to connect to your computer). These machines ask the DNS server (which they also know from the campus DHCP) for the IP address of [email protected] and the DNS server returns the corresponding IP address.

You'd need to make a DHCP reservation to get the same IP address always, but this only administrators can do.

You can check it with command-line:

dig +noall +answer -x <your_ip_address>

or if you know your interface name (en0 in the below example) automatically:

dig +noall +answer -x `ipconfig getifaddr en0`

It's the PTR record (reverse DNS) corresponding to the IP address which your computer was assigned via DHCP. It changes each time your computer gets a new address from DHCP and you can't make it static.

The problem here is not in the settings on your computer, but on all the other computers connected to the campus network (i.e. computers try to connect to your computer). These machines ask the DNS server (which they also know from the campus DHCP) for the IP address of [email protected] and the DNS server returns the corresponding IP address.

You'd need to make a DHCP reservation to get the same IP address always, but this only administrators can do.

You can check it with command-line:

dig +short -x <your_ip_address>

or if you know your interface name (en0 in the below example) automatically:

dig +short -x `ipconfig getifaddr en0`

It's the PTR record (reverse DNS) corresponding to the IP which your computer was assigned via DHCP.

  It changes each time your computer gets a new address from DHCP and you can't make it static. The problem here is not in the settings on your computer, but on all the other computers connected to the campus network (i.e. computers try to connect to your computer). These machines ask DNS server for the IP address of [email protected] and DNS server gives them the corresponding IP address.

You'd need to make a DHCP reservation to get the same IP address always, but this only administrators can do.

You can check it with command-line:

dig -x <your_ip_address>

or if you know your interface name (here en0) automatically:

dig -x `ipconfig getifaddr en0`

It's the PTR record (reverse DNS) corresponding to the IP address which your computer was assigned via DHCP. It changes each time your computer gets a new address from DHCP and you can't make it static. 

The problem here is not in the settings on your computer, but on all the other computers connected to the campus network (i.e. computers try to connect to your computer). These machines ask the DNS server (which they also know from the campus DHCP) for the IP address of [email protected] and the DNS server returns the corresponding IP address.

You'd need to make a DHCP reservation to get the same IP address always, but this only administrators can do.

You can check it with command-line:

dig +noall +answer -x <your_ip_address>

or if you know your interface name (en0 in the below example) automatically:

dig +noall +answer -x `ipconfig getifaddr en0`

It's the PTR record (reverse DNS) corresponding to the IP which your computer was assigned via DHCP. It changes each time your computer gets a new address.

You can check it with command-line:

dig -x <your_ip_address>

or if you know your interface name (here en0) automatically:

dig -x `ipconfig getifaddr en0`

It's the PTR record (reverse DNS) corresponding to the IP which your computer was assigned via DHCP. 

It changes each time your computer gets a new address from DHCP and you can't make it static. The problem here is not in the settings on your computer, but on all the other computers connected to the campus network (i.e. computers try to connect to your computer). These machines ask DNS server for the IP address of [email protected] and DNS server gives them the corresponding IP address.

You'd need to make a DHCP reservation to get the same IP address always, but this only administrators can do.

You can check it with command-line:

dig -x <your_ip_address>

or if you know your interface name (here en0) automatically:

dig -x `ipconfig getifaddr en0`