[BUG] Kubernetes runner couldn't resolve host

I'm running GitlabCE and GitlabRunner both with Kubernetes's PODS and it seems like the runner use Pod name as url (gitlab-2204439088-skp5l) and that's why it couldn't resolve.

Shouldn't it be service name? like http://gitlab-ci-token:xxxxxxxxxxxxxxxxxxxx@namespace.service-name.svc:80

Here is my log.

Running with gitlab-ci-multi-runner 9.3.0 (3df822b)
  on Kubernetes Runner (f9b5bc88)
Using Kubernetes namespace: gitlab
Using Kubernetes executor with image docker:latest ...
Waiting for pod gitlab/runner-f9b5bc88-project-1-concurrent-0h23s6 to be running, status is Pending
.
.
.
Waiting for pod gitlab/runner-f9b5bc88-project-1-concurrent-0h23s6 to be running, status is Pending
Running on runner-f9b5bc88-project-1-concurrent-0h23s6 via gitlab-runner-3653620256-tmglp...
Cloning repository...
Cloning into '/root/cidi'...
fatal: unable to access 'http://gitlab-ci-token:xxxxxxxxxxxxxxxxxxxx@gitlab-2204439088-skp5l/root/cidi.git/': Couldn't resolve host 'gitlab-2204439088-skp5l'
ERROR: Job failed: error executing remote command: command terminated with non-zero exit code: Error executing in Docker Container: 1

The above logs clone from http://gitlab-ci-token:xxxxxxxxxxxxxxxxxxxx@gitlab-2204439088-skp5l/root/cidi.git/ instead, it should clone from http://gitlab-ci-token:xxxxxxxxxxxxxxxxxxxx@gitlat.gitlab.svc:80/root/cidi.git/

(namespace is gitlab nad svc name is gitlab too.)