nigeldodd

Ok, thank you. I think it is clear that it cannot be done straightforwardly from the backend as I would have hoped.

thanks, but I may not have explained the issue sufficiently to you. Here is the source code for the top of the index.php page as rendered by WordPress:

<link rel="pingback" href="http://192.168.0.103/wordpress/xmlrpc.php">
        <!--[if lt IE 9]>
        <script src="http://192.168.0.103/wordpress/wp-content/themes/twentyfifteen/js/html5.js"></script>
        <![endif]-->
        <script>(function(){document.documentElement.className='js'})();</script>
        <title>raspberry site | Nigel and William's site</title>
<link rel="alternate" type="application/rss+xml" title="raspberry site
&raquo; Feed" href="http://192.168.0.103/wordpress/?feed=rss2" />
<link rel="alternate" type="application/rss+xml" title="raspberry site
&raquo; Comments Feed"
href="http://192.168.0.103/wordpress/?feed=comments-rss2" />

You can see the hard coded 192.168.0.103 which is no longer relevant since the router has dished up another ip address. The problem is with the hard wired ip addresses and I am surprised WordPress uses these for obvious reasons.

Which file or which table in the database will contain 192.168.0.103 please?