check externalNameService more time

[JornShen]

What type of PR is this?

/kind bug

What this PR does / why we need it:

add more check to externalNameService

the failed test error as fellow:

Jan 15 09:43:03.808: INFO: Creating new exec pod
Jan 15 09:43:08.368: INFO: Running '/workspace/kubernetes/platforms/linux/amd64/kubectl --server=https://34.105.6.162 --kubeconfig=/workspace/.kube/config --namespace=services-5563 exec execpod4sxhv -- /bin/sh -x -c nslookup clusterip-service.services-5563.svc.cluster.local'
Jan 15 09:43:10.121: INFO: rc: 1
Jan 15 09:43:10.121: FAIL: Unexpected error:
    <*errors.errorString | 0xc002cf2840>: {
        s: "ExternalName service \"services-5563/execpod4sxhv\" must resolve to IP",
    }
    ExternalName service "services-5563/execpod4sxhv" must resolve to IP
occurred

Full Stack Trace
k8s.io/kubernetes/test/e2e/network.glob..func24.17()
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:1773 +0x465
k8s.io/kubernetes/test/e2e.RunE2ETests(0xc0038b8480)
	_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c
k8s.io/kubernetes/test/e2e.TestE2E(0xc0038b8480)
	_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:144 +0x2b
testing.tRunner(0xc0038b8480, 0x4fe76e8)
	/usr/local/go/src/testing/testing.go:1123 +0xef
created by testing.(*T).Run
	/usr/local/go/src/testing/testing.go:1168 +0x2b3

It failed in checking externalName type service effective.
And I found the case only check it once.

kubernetes/test/e2e/framework/service/jig.go

Line 991 in 9f2f1b8

_, stderr, err := framework.RunHostCmdWithFullOutput(pod.Namespace, pod.Name, cmd)

I think check it once is not enough. The work item is DNS side. But we can control the order of dns work completed and
our check. So add more check times will be more reasonable.

Which issue(s) this PR fixes:

Fix #98104

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

@JornShen: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[JornShen]

/cc @aojea @spiffxp

[JornShen]

updated. PTAL :)
@aojea

[aojea]

/lgtm
/assign @MrHohn

[JornShen]

/test pull-kubernetes-e2e-kind

[MrHohn]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JornShen, MrHohn

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• test/e2e/framework/OWNERS [MrHohn]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[fejta-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

[k8s-ci-robot]

@JornShen: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
pull-kubernetes-e2e-ubuntu-gce-network-policies	6d084f25d2aa30cb83634dd9391409bd8a6c3302	link	/test pull-kubernetes-e2e-ubuntu-gce-network-policies

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[aojea]

/retest
storage flake