Dubbo registers zookepper magic IP

Use Dubbo to register the service on zookepper. the IP address of the Dubbo server is 192.168.70.105.

In zookepper, the service provider is

dubbo://202.102.110.203:8083/com.paycenter.api.IPayService?anyhost=true&application=pay-center-service&check=false&codec=dubbo&default.cluster=failover&default.executes=40&default.loadbalance=leastactive&default.retries=2&default.timeout=65000&dubbo=2.6.9&generic=false&group=ebus_dev&heartbeat=60000&interface=com.easyway.ebus.paycenter.api.IPayService&methods=getPayUrl,refund,royalty,getBankList,getAllPayAccountBySite&organization=EasyWayDev&owner=Gengyichao&pid=5564&revision=1.0.2&side=consumer&timeout=6000×tamp=1410590266743&version=0.6.0

An IP address of 202.102.110.203 is displayed.

No matter how you restart zookepper, tomcat, server, or Nic, it cannot be changed. Because the IP address 202.102.110.203 does not exist, the service consumer cannot find the registered service.

Occasionally, I found that the IP address registered to zookepper in my notebook 192.168.45.155 was 169.254.125.122. Then I began to study how my laptop came up with this IP address. Later I found it was the IP address of the local virtual network card, instead of using the IP address, it is estimated that zookepper registration may be based on the IP address of the first NIC (including the virtual Nic) on the machine.

Return to 192.168.70.105, which is the second network card. Then, change the IP address to the first network card and change the network cable. The problem is normal (later I found that this is not the reason)

In a few days, I found that all the other machine registration services except 105 machines are 202.102.110.203. I am determined to find out the real cause.

Because the events in the previous notes thought it was a dual-nic, and the network adapter may not work with an automatic IP address, the two network adapters on the server are inserted into the network. The fault persists and neither IP address can be registered.

When a nonexistent URL is pinged occasionally, the system automatically parses 202.102.110.203.

It's probably about DNS.

Sure enough VI/etc/resolv. conf

The nameserver has a DNS address, but the server does not need to access the Internet on the Intranet. Change the nameserver to the gateway 192.168.70.1. Everything is normal. The other servers have been changed and started.

Dubbo registers zookepper magic IP